Communications Default Fields

Default fields contain customer-specific information from the CMP Converged Monetisation Platform. The MDS Global product that supports customer care and billing for digital service providers. database that can be included in communications with end users. Business Configuration A module in the CMP Administation console that provides for viewing and modification of business and user applicable system configuration. allows you to define and maintain these default fields.

Default fields are associated with beans, which are the software objects that retrieve the data from CMP. When CMP processes a communication, it checks which field needs to be populated for that particular communication and then invokes the associated beans, which fetch the data from the CMP database according to the configured parameters. The bean parameter identifies the exact piece of information that the bean should retrieve. For example, the parameter SubscriptionUserName to the Subscription A billing entity that incurs a charge. Examples include a network attached device whose usage you want to measure and charge for, or a monthly software subscription bean is used to retrieve the SubscriptionUserName field from the Subscription table. Parameters can be any customer-specific attribute supported by the bean, such as a field, static text, a value, or a date. For example the WORKFLOWBEAN supports the following parameters:

• Event
• Total SL Adjustments
• Resolved Date
• Resolution Required By Date.

When CMP is being used in conjunction with an Online Charging System (OCS), the OCS sends notifications to subscribers when they have exceeded their allowance threshold. The CMP OCSNOTIFICATIONATTRIBUTES bean allows the attributes provided within the Openet notification to be used to enrich the outbound communication with subscriber The end user of a network. information held within CMP. The following CMP attributes can be used:

• Allowance Description
• Allowance Type (Data, Voice, Text or Cash)
• Spend Cap Description
• Formatted values for entitlement size, usage The consumption of services, for example a subscriber using call minutes. amount and remaining quota. Formatting is based on the type of allowance.

Default fields can be configured with beans that have multiple parameters. When you supply multiple parameters for a bean, they must be separated with commas.

Configuration of a default field requires the following:

• Supplying a code and description for the default field.
• Choosing a category for the information in the field, for example static text, account In the Cloud Monetisation Platform, a billing entity that can be used to manage payments on one or more subscriptions or payments for services. An account can hold details such as payments or invoices. or financial.
• Selecting the levels in the customer In the context of the Cloud Monetisation Platform, an individual or organisation who has signed an agreement to take goods and services from a service provider. A customer receives a bill associated with one or more subscriptions, and can be a single end user or a large company with many subscriptions assigned to one agreement. hierarchy at which the field is supported.
• Selecting the bean (the software object) that will retrieve the field information from CMP.
• Indicating whether the data source is internal or external.
• Specifying a parameter that tells the bean what information to retrieve. Beans can have multiple parameters.
• Specifying a maximum length for the field. This is used to calculate whether an SMS Short Message Service. A text messaging service component of most mobile telephone systems. SMS uses standardized communication protocols to enable mobile phone devices to exchange short text messages. message with fields will be longer than the 140 characters valid for a single SMS.
• Specifying whether the field is active.

For more information, see the CMP Business Configuration Overview. For more information on configuring default fields, see the online help for the Business Configuration console.

Some communication formats, for example letters and emails, must be associated with an additional external template that determines the format, style and layout of the correspondence. Templates contain elements such as static text, images, headers and footers, and dynamic text or merge fields. The merge fields are populated with the attributes from the CMP default fields. When you compose an external template, you must reference the default fields correctly. For information on how to do this, see Working with Email and Letter Templates.